I have been unsuccessful so far in finding a way to open a controlled module for "Unmanaged Edit" mode via DXL. Support doesn't seem to have any ideas either. Has anyone figured out a way to do this?
tdperry_99 - Fri Feb 25 10:26:59 EST 2011 |
|
Re: How to Open Controlled Modules in Unmanaged Mode?
SystemAdmin - Fri Feb 25 10:40:14 EST 2011
Sorry, but what is a "controlled module" and what is "unmanaged edit"? What do they mean for you?
|
|
Re: How to Open Controlled Modules in Unmanaged Mode?
tdperry_99 - Fri Feb 25 10:59:06 EST 2011
Re-reading my post, I realize I left out a lot of details.
We use the DOORS-Change Integration, which allows you to place DOORS modules under CM control. With a module under CM control, a user would need to have a RCR (similar to a CR) in Change assigned to them in order to make changes to the module. When I mentioned controlled modules, I was referring to modules that are under CM control via this integration.
One feature of the integration is the ability to open controlled modules in "Unmanaged Edit" mode. This allows you to make changes to particular attributes without the need for a RCR assigned to you.
Sorry for the confusion.
|
|
Re: How to Open Controlled Modules in Unmanaged Mode?
SystemAdmin - Fri Feb 25 11:18:41 EST 2011 tdperry_99 - Fri Feb 25 10:59:06 EST 2011
Re-reading my post, I realize I left out a lot of details.
We use the DOORS-Change Integration, which allows you to place DOORS modules under CM control. With a module under CM control, a user would need to have a RCR (similar to a CR) in Change assigned to them in order to make changes to the module. When I mentioned controlled modules, I was referring to modules that are under CM control via this integration.
One feature of the integration is the ability to open controlled modules in "Unmanaged Edit" mode. This allows you to make changes to particular attributes without the need for a RCR assigned to you.
Sorry for the confusion.
You can not (or can you, does somebody know?) disable triggers in DXL after you have started DOORS client. You can disable them before starting a DOORS client with a -T switch in the DOORS client startup ommand. To do this you have to be a DOORS Database Manager or have rights to manage the database.
For more info on command line switches see this page (this is for version 9.3 but applies also to other versions).
|
|
Re: How to Open Controlled Modules in Unmanaged Mode?
llandale - Fri Feb 25 15:54:39 EST 2011 SystemAdmin - Fri Feb 25 11:18:41 EST 2011
OK, the Change integration is managed by DOORS triggers. Probably the "Unmanaged mode" means disabling these triggers.
You can not (or can you, does somebody know?) disable triggers in DXL after you have started DOORS client. You can disable them before starting a DOORS client with a -T switch in the DOORS client startup ommand. To do this you have to be a DOORS Database Manager or have rights to manage the database.
For more info on command line switches see this page (this is for version 9.3 but applies also to other versions).
I've also had some luck having a DXL communicate with pre-attr-save triggers, such that the trigger code is designed to stop changes to attributes unless triggers are off; and the trigger itself checks the state of whether triggers are off; thus the DXL can modify the attr-values by turning off triggers, making the change, and turning them back on; thus our Standard folks can use the DXL to modify the values, but cannot modify them directly.
Unless they are clever and read this post and come to the obvious deduction, but gratefully none of them can read.
|
|
Re: How to Open Controlled Modules in Unmanaged Mode?
SystemAdmin - Fri Feb 25 23:06:02 EST 2011 llandale - Fri Feb 25 15:54:39 EST 2011
Some time ago I posted a clever "TriggerState.dxl" script that turns triggers on and off. Its 90% comments that are worth reading. In this case you can turn triggers off for "Standard" folks but the triggers still fire. Confused? Well, triggers for standard folks ignore the flag and always run and therefore you cannot use this method for this purpose for Standard folks.
I've also had some luck having a DXL communicate with pre-attr-save triggers, such that the trigger code is designed to stop changes to attributes unless triggers are off; and the trigger itself checks the state of whether triggers are off; thus the DXL can modify the attr-values by turning off triggers, making the change, and turning them back on; thus our Standard folks can use the DXL to modify the values, but cannot modify them directly.
Unless they are clever and read this post and come to the obvious deduction, but gratefully none of them can read.
Paul Miller
Melbourne, Australia
|
|